Subslot bundling and acknowledgement

ABSTRACT

A first apparatus may puncture, in at least two subslots, a first type of data or control information with a second type of data or control information. The first apparatus may bundle the least two subslots within a subframe, and the subframe may include a portion for carrying acknowledgment (ACK)/negative acknowledgment (NACK) information associated with the second type of data or control information. The first apparatus may communicate with a user equipment (UE) during the at least two subslots within the subframe. A second apparatus may receive ACK/NACK information associated with a second type of data or control information. The second apparatus may reduce a transmission power for a first type of data or control information during a subsequent subframe when the ACK/NACK information indicates a negative acknowledgement.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is a continuation of U.S. application Ser. No.15/789,489, entitled “SUBSLOT BUNDLING AND ACKNOWLEDGEMENT” and filed onOct. 20, 2017. This application claims the benefit of U.S. applicationSer. No. 15/789,489, entitled “SUBSLOT BUNDLING AND ACKNOWLEDGEMENT” andfiled on Oct. 20, 2017, and U.S. Provisional Application Ser. No.62/435,518, entitled “SUBSLOT BUNDLING AND ACKNOWLEDGEMENT” and filed onDec. 16, 2016, each of which is expressly incorporated by referenceherein in its entirety.

BACKGROUND Field

The present disclosure relates generally to communication systems, andmore particularly, to a base station configured to bundle subslots.

Background

Wireless communication systems are widely deployed to provide varioustelecommunication services such as telephony, video, data, messaging,and broadcasts. Typical wireless communication systems may employmultiple-access technologies capable of supporting communication withmultiple users by sharing available system resources. Examples of suchmultiple-access technologies include code division multiple access(CDMA) systems, time division multiple access (TDMA) systems, frequencydivision multiple access (FDMA) systems, orthogonal frequency divisionmultiple access (OFDMA) systems, single-carrier frequency divisionmultiple access (SC-FDMA) systems, and time division synchronous codedivision multiple access (TD-SCDMA) systems.

These multiple access technologies have been adopted in varioustelecommunication standards to provide a common protocol that enablesdifferent wireless devices to communicate on a municipal, national,regional, and even global level. An example telecommunication standardis Long Term Evolution (LTE). LTE is a set of enhancements to theUniversal Mobile Telecommunications System (UMTS) mobile standardpromulgated by Third Generation Partnership Project (3GPP). LTE isdesigned to support mobile broadband access through improved spectralefficiency, lowered costs, and improved services using OFDMA on thedownlink, SC-FDMA on the uplink, and multiple-input multiple-output(MIMO) antenna technology. However, as the demand for mobile broadbandaccess continues to increase, there exists a need for furtherimprovements in LTE technology. These improvements may also beapplicable to other multi-access technologies and the telecommunicationstandards that employ these technologies.

An example of an improvement to LTE may include fifth generationwireless systems and mobile networks (5G). 5G is a telecommunicationsstandard that may extend beyond LTE and/or 4G standards. For example, 5Gmay offer higher capacity and, therefore, serve a larger number of usersin an area. Further, 5G may improve data consumption and data rates.

SUMMARY

The following presents a simplified summary of one or more aspects inorder to provide a basic understanding of such aspects. This summary isnot an extensive overview of all contemplated aspects, and is intendedto neither identify key or critical elements of all aspects nordelineate the scope of any or all aspects. Its sole purpose is topresent some concepts of one or more aspects in a simplified form as aprelude to the more detailed description that is presented later.

In an aspect of the disclosure, a first method, a firstcomputer-readable medium, and a first apparatus are provided. The firstapparatus may puncture, in at least two subslots, a first type of dataor control information with a second type of data or controlinformation. The first apparatus may bundle the least two subslotswithin a subframe, and the subframe may include a portion for carryingacknowledgment (ACK)/negative acknowledgment (NACK) informationassociated with the second type of data or control information. Thefirst apparatus may communicate with a user equipment (UE) during the atleast two subslots within the subframe.

In another aspect of the disclosure, a second method, a secondcomputer-readable medium, and a second apparatus are provided. Thesecond apparatus may receive ACK/NACK information associated with asecond type of data or control information. The second apparatus mayreduce a transmission power for a first type of data or controlinformation during a subsequent subframe when the ACK/NACK informationindicates a negative acknowledgement.

In another aspect of the disclosure, a third method, a thirdcomputer-readable medium, and a third apparatus are provided. The thirdapparatus may receive a second type of data or control informationcarried in at least two subslots bundled within a subframe, and thesecond type of data or control information may be punctured into a firsttype of data or control information. The subframe may include a portionfor carrying ACK/NACK information associated with the second type ofdata or control information. The third apparatus may determine ACK/NACKinformation for the second type of data or control information carriedin the bundled at least two subslots. The third apparatus may send theACK/NACK information during the portion of the subframe for carryingACK/NACK information.

To the accomplishment of the foregoing and related ends, the one or moreaspects comprise the features hereinafter fully described andparticularly pointed out in the claims. The following description andthe annexed drawings set forth in detail certain illustrative featuresof the one or more aspects. These features are indicative, however, ofbut a few of the various ways in which the principles of various aspectsmay be employed, and this description is intended to include all suchaspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating an example of a wireless communicationssystem and an access network.

FIGS. 2A, 2B, 2C, and 2D are diagrams illustrating LTE examples of a DLframe structure, DL channels within the DL frame structure, an UL framestructure, and UL channels within the UL frame structure, respectively.

FIG. 3 is a diagram illustrating an example of a base station and userequipment (UE) in an access network.

FIG. 4 is a diagram of a wireless communications system.

FIG. 5 is a diagram of a subframe structure.

FIG. 6 is a diagram of a subslot configuration.

FIG. 7 is a diagram of a subslot configuration.

FIG. 8 is a diagram of a subslot configuration.

FIG. 9 is a flowchart of a method of wireless communication.

FIG. 10 is a flowchart of a method of wireless communication.

FIG. 11 is a flowchart of a method of wireless communication.

FIG. 12 is a conceptual data flow diagram illustrating the data flowbetween different means/components in an exemplary apparatus.

FIG. 13 is a diagram illustrating an example of a hardwareimplementation for an apparatus employing a processing system.

FIG. 14 is a conceptual data flow diagram illustrating the data flowbetween different means/components in an exemplary apparatus.

FIG. 15 is a diagram illustrating an example of a hardwareimplementation for an apparatus employing a processing system.

FIG. 16 is a conceptual data flow diagram illustrating the data flowbetween different means/components in an exemplary apparatus.

FIG. 17 is a diagram illustrating an example of a hardwareimplementation for an apparatus employing a processing system.

DETAILED DESCRIPTION

The detailed description set forth below in connection with the appendeddrawings is intended as a description of various configurations and isnot intended to represent the only configurations in which the conceptsdescribed herein may be practiced. The detailed description includesspecific details for the purpose of providing a thorough understandingof various concepts. However, it will be apparent to those skilled inthe art that these concepts may be practiced without these specificdetails. In some instances, well known structures and components areshown in block diagram form in order to avoid obscuring such concepts.

Several aspects of telecommunication systems will now be presented withreference to various apparatus and methods. These apparatus and methodswill be described in the following detailed description and illustratedin the accompanying drawings by various blocks, components, circuits,processes, algorithms, etc. (collectively referred to as “elements”).These elements may be implemented using electronic hardware, computersoftware, or any combination thereof. Whether such elements areimplemented as hardware or software depends upon the particularapplication and design constraints imposed on the overall system.

By way of example, an element, or any portion of an element, or anycombination of elements may be implemented as a “processing system” thatincludes one or more processors. Examples of processors includemicroprocessors, microcontrollers, graphics processing units (GPUs),central processing units (CPUs), application processors, digital signalprocessors (DSPs), reduced instruction set computing (RISC) processors,systems on a chip (SoC), baseband processors, field programmable gatearrays (FPGAs), programmable logic devices (PLDs), state machines, gatedlogic, discrete hardware circuits, and other suitable hardwareconfigured to perform the various functionality described throughoutthis disclosure. One or more processors in the processing system mayexecute software. Software shall be construed broadly to meaninstructions, instruction sets, code, code segments, program code,programs, subprograms, software components, applications, softwareapplications, software packages, routines, subroutines, objects,executables, threads of execution, procedures, functions, etc., whetherreferred to as software, firmware, middleware, microcode, hardwaredescription language, or otherwise.

Accordingly, in one or more example embodiments, the functions describedmay be implemented in hardware, software, or any combination thereof. Ifimplemented in software, the functions may be stored on or encoded asone or more instructions or code on a computer-readable medium.Computer-readable media includes computer storage media. Storage mediamay be any available media that can be accessed by a computer. By way ofexample, and not limitation, such computer-readable media can comprise arandom-access memory (RAM), a read-only memory (ROM), an electricallyerasable programmable ROM (EEPROM), optical disk storage, magnetic diskstorage, other magnetic storage devices, combinations of theaforementioned types of computer-readable media, or any other mediumthat can be used to store computer executable code in the form ofinstructions or data structures that can be accessed by a computer.

FIG. 1 is a diagram illustrating an example of a wireless communicationssystem and an access network 100. The wireless communications system(also referred to as a wireless wide area network (WWAN)) includes basestations 102, UEs 104, and an Evolved Packet Core (EPC) 160. The basestations 102 may include macro cells (high power cellular base station)and/or small cells (low power cellular base station). The macro cellsinclude eNBs. The small cells include femtocells, picocells, andmicrocells.

The base stations 102 (collectively referred to as Evolved UniversalMobile Telecommunications System (UMTS) Terrestrial Radio Access Network(E-UTRAN)) interface with the EPC 160 through backhaul links 132 (e.g.,S1 interface). In addition to other functions, the base stations 102 mayperform one or more of the following functions: transfer of user data,radio channel ciphering and deciphering, integrity protection, headercompression, mobility control functions (e.g., handover, dualconnectivity), inter-cell interference coordination, connection setupand release, load balancing, distribution for non-access stratum (NAS)messages, NAS node selection, synchronization, radio access network(RAN) sharing, multimedia broadcast multicast service (MBMS), subscriberand equipment trace, RAN information management (RIM), paging,positioning, and delivery of warning messages. The base stations 102 maycommunicate directly or indirectly (e.g., through the EPC 160) with eachother over backhaul links 134 (e.g., X2 interface). The backhaul links134 may be wired or wireless.

The base stations 102 may wirelessly communicate with the UEs 104. Eachof the base stations 102 may provide communication coverage for arespective geographic coverage area 110. There may be overlappinggeographic coverage areas 110. For example, the small cell 102′ may havea coverage area 110′ that overlaps the coverage area 110 of one or moremacro base stations 102. A network that includes both small cell andmacro cells may be known as a heterogeneous network. A heterogeneousnetwork may also include Home Evolved Node Bs (eNBs) (HeNBs), which mayprovide service to a restricted group known as a closed subscriber group(CSG). The communication links 120 between the base stations 102 and theUEs 104 may include uplink (UL) (also referred to as reverse link)transmissions from a UE 104 to a base station 102 and/or downlink (DL)(also referred to as forward link) transmissions from a base station 102to a UE 104. The communication links 120 may use MIMO antennatechnology, including spatial multiplexing, beamforming, and/or transmitdiversity. The communication links may be through one or more carriers.The base stations 102/UEs 104 may use spectrum up to Y MHz (e.g., 5, 10,15, 20 MHz) bandwidth per carrier allocated in a carrier aggregation ofup to a total of Yx MHz (x component carriers) used for transmission ineach direction. The carriers may or may not be adjacent to each other.Allocation of carriers may be asymmetric with respect to DL and UL(e.g., more or less carriers may be allocated for DL than for UL). Thecomponent carriers may include a primary component carrier and one ormore secondary component carriers. A primary component carrier may bereferred to as a primary cell (PCell) and a secondary component carriermay be referred to as a secondary cell (SCell).

The wireless communications system may further include a Wi-Fi accesspoint (AP) 150 in communication with Wi-Fi stations (STAs) 152 viacommunication links 154 in a 5 GHz unlicensed frequency spectrum. Whencommunicating in an unlicensed frequency spectrum, the STAs 152/AP 150may perform a clear channel assessment (CCA) prior to communicating inorder to determine whether the channel is available.

The small cell 102′ may operate in a licensed and/or an unlicensedfrequency spectrum. When operating in an unlicensed frequency spectrum,the small cell 102′ may employ LTE and use the same 5 GHz unlicensedfrequency spectrum as used by the Wi-Fi AP 150. The small cell 102′,employing LTE in an unlicensed frequency spectrum, may boost coverage toand/or increase capacity of the access network. LTE in an unlicensedspectrum may be referred to as LTE-unlicensed (LTE-U), licensed assistedaccess (LAA), or MuLTEfire.

The wireless communications system and an access network 100 may includea base station 180, which may be a millimeter wave (mmW) base station.In one aspect, the mmW base station 180 may be integrated with anotherbase station, such as a cellular base station, eNB, and the like. ThemmW base station 180 may operate in mmW frequencies and/or near mmWfrequencies in communication with the UE 182. Extremely high frequency(EHF) is part of the RF in the electromagnetic spectrum. EHF has a rangeof 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10millimeters. Radio waves in the band may be referred to as a millimeterwave. Near mmW may extend down to a frequency of 3 GHz with a wavelengthof 100 millimeters. The super high frequency (SHF) band extends between3 GHz and 30 GHz, also referred to as centimeter wave. Communicationsusing the mmW/near mmW radio frequency band has extremely high path lossand a short range. The mmW base station 180 may utilize beamforming 184with the UE 182 to compensate for the extremely high path loss and shortrange.

The EPC 160 may include a Mobility Management Entity (MME) 162, otherMMEs 164, a Serving Gateway 166, a Multimedia Broadcast MulticastService (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC)170, and a Packet Data Network (PDN) Gateway 172. The MME 162 may be incommunication with a Home Subscriber Server (HSS) 174. The MME 162 isthe control node that processes the signaling between the UEs 104 andthe EPC 160. Generally, the MME 162 provides bearer and connectionmanagement. All user Internet protocol (IP) packets are transferredthrough the Serving Gateway 166, which itself is connected to the PDNGateway 172. The PDN Gateway 172 provides UE IP address allocation aswell as other functions. The PDN Gateway 172 and the BM-SC 170 areconnected to the IP Services 176. The IP Services 176 may include theInternet, an intranet, an IP Multimedia Subsystem (IMS), a PS StreamingService (PSS), and/or other IP services. The BM-SC 170 may providefunctions for MBMS user service provisioning and delivery. The BM-SC 170may serve as an entry point for content provider MBMS transmission, maybe used to authorize and initiate MBMS Bearer Services within a publicland mobile network (PLMN), and may be used to schedule MBMStransmissions. The MBMS Gateway 168 may be used to distribute MBMStraffic to the base stations 102 belonging to a Multicast BroadcastSingle Frequency Network (MBSFN) area broadcasting a particular service,and may be responsible for session management (start/stop) and forcollecting eMBMS related charging information.

The base station may also be referred to as a Node B, evolved Node B(eNB), an access point, a base transceiver station, a radio basestation, a radio transceiver, a transceiver function, a basic serviceset (BSS), an extended service set (ESS), or some other suitableterminology. The base station 102 provides an access point to the EPC160 for a UE 104. Examples of UEs 104 include a cellular phone, a smartphone, a session initiation protocol (SIP) phone, a laptop, a personaldigital assistant (PDA), a satellite radio, a global positioning system,a multimedia device, a video device, a digital audio player (e.g., MP3player), a camera, a game console, a tablet, a smart device, a wearabledevice, or any other similar functioning device. The UE 104 may also bereferred to as a station, a mobile station, a subscriber station, amobile unit, a subscriber unit, a wireless unit, a remote unit, a mobiledevice, a wireless device, a wireless communications device, a remotedevice, a mobile subscriber station, an access terminal, a mobileterminal, a wireless terminal, a remote terminal, a handset, a useragent, a mobile client, a client, or some other suitable terminology.

Referring again to FIG. 1, in certain aspects, the first base station102 may neighbor the second base station 180. Consequently, the secondbase station 180 may cause interference to communication between the UE104 and the first base station 102. For example, the second base station180 may cause interference to acknowledgement (ACK)/negativeacknowledgement (NACK) information communicated by the UE 104 to thefirst base station 102 in response to downlink transmissions from thefirst base station 102. Therefore, the communication between the firstbase station 102 and the UE 104 may benefit from one or more operationsthat mitigate interference.

In various aspects, the first base station 102 may configure a subframewith a subslot configuration that includes a plurality of subslots, andeach subslot may have a number of symbols (e.g., a duration) that isless than a number of symbols included in each subframe. Each subframemay include a portion for carrying ACK/NACK information. In aspects, thefirst base station 102 may puncture, in at least two subslots includedin a subframe, a first type of data or control information with a secondtype of data or control information. For example, the first base station102 may puncture, in at least two subslots included in a subframe, dataor control information associated with enhanced mobile broadband (eMBB)with data or control information associated with ultra-reliablelow-latency communication (URLLC). In aspects, the first base station102 may bundle the at least two subslots within a subframe, and theACK/NACK portion of the subframe may be used to carry ACK/NACKinformation associated with the second type of data or controlinformation carried in the bundled at least two subslots 198. In anaspect, the first base station 102 may communicate the second type ofdata or control information with the UE 104 during the bundled at leasttwo subslots 198.

In aspects, the UE 104 may receive the second type of data or controlinformation during the bundled subslots 198. The UE 104 may determineACK/NACK information for the second type of data or control informationcarried in the bundled at least two subslots 198. For example, the UE104 may determine an ACK when the UE 104 is able to successfully decodethe second type of data or control information carried in the bundledsubslots 198. However, the UE 104 may determine a NACK when the UE 104is unable to successfully decode the second type of data or controlinformation carried in the bundled subslots 198. The UE 104 may thensend the ACK/NACK information during the portion of the subframe forcarrying ACK/NACK information. In an aspect, the UE 104 may send theACK/NACK information on an uplink common burst (UCB) channel, which mayalso be known in some aspects as an eMBB UCB channel.

When the first base station 102 receives a NACK associated with thesecond type of data or control information carried in the bundled atleast two subslots 198, the first base station 102 may determine thatthe second type of data or control information is to be retransmitted tothe UE 104, for example, because the UE 104 was unable to decode thesecond type of data or control information carried in the bundledsubslots 198. Accordingly, the first base station 102 may reschedule thesecond type of data or control information and send the rescheduledsecond type of data or control information to the UE 104.

While the ACK/NACK information sent by the UE 104 may be intended forthe first base station 102, the second base station 180 may also receivethe ACK/NACK information from the UE 104, for example, due to theproximity of the second base station 180 to the first base station 102and/or the UE 104. Based on the reception of the ACK/NACK information,the second base station 180 may be configured to reduce a transmissionpower for a first type of data or control information (e.g., eMBB dataor control information) during a subsequent subframe. For example, theACK/NACK information may indicate a negative acknowledgement, andtherefore the second base station 180 may reduce a transmission powerduring a subsequent subframe (e.g., when the first base station 102transmits the rescheduled second type of data or control information),for example, in order to mitigate interference that the second basestation 180 may otherwise introduce when the second type of data orcontrol information is retransmitted by the first base station 102 tothe UE 104. In one aspect, the second base station 180 may reducetransmission power by yielding transmission of the first type of data orcontrol information (e.g., the second base station 180 may delaytransmission of the first type of data or control information until thefirst base station 180 retransmits the second type of data or controlinformation).

In order for the second base station 180 to detect the ACK/NACKinformation from the UE 104, the first base station 102 may send, to thesecond base station 102, information associated with the ACK/NACKconfiguration. The first base station 102 may send the informationindicating the configuration using a backhaul link 134 (e.g., via the X2interface).

Accordingly, the first base station 102 may send, to the second basestation 180, information indicating a configuration of the portion forcarrying the ACK/NACK information associated with the second type ofdata or control information. The information indicating theconfiguration may include, for example, an indication of one or moreresources on which the ACK/NACK information may be carried. For example,the first base station 102 may indicate, to the second base station 180,information indicating one or more symbols during which the ACK/NACKinformation may be carried (e.g., the last symbol of a subframe). In oneaspect, the first base station 102 may indicate, to the second basestation 180, a channel on which the ACK/NACK information is to becarried, such as an UCB channel.

FIG. 2A is a diagram 200 illustrating an example of a DL frame structurein LTE. FIG. 2B is a diagram 230 illustrating an example of channelswithin the DL frame structure in LTE. FIG. 2C is a diagram 250illustrating an example of an UL frame structure in LTE. FIG. 2D is adiagram 280 illustrating an example of channels within the UL framestructure in LTE. Other wireless communication technologies may have adifferent frame structure and/or different channels. In LTE, a frame (10ms) may be divided into 10 equally sized subframes. Each subframe mayinclude two consecutive time slots. A resource grid may be used torepresent the two time slots, each time slot including one or more timeconcurrent resource blocks (RBs) (also referred to as physical RBs(PRBs)). The resource grid is divided into multiple resource elements(REs). In LTE, for a normal cyclic prefix, an RB contains 12 consecutivesubcarriers in the frequency domain and 7 consecutive symbols (for DL,OFDM symbols; for UL, SC-FDMA symbols) in the time domain, for a totalof 84 REs. For an extended cyclic prefix, an RB contains 12 consecutivesubcarriers in the frequency domain and 6 consecutive symbols in thetime domain, for a total of 72 REs. The number of bits carried by eachRE depends on the modulation scheme.

As illustrated in FIG. 2A, some of the REs carry DL reference (pilot)signals (DL-RS) for channel estimation at the UE. The DL-RS may includecell-specific reference signals (CRS) (also sometimes called common RS),UE-specific reference signals (UE-RS), and channel state informationreference signals (CSI-RS). FIG. 2A illustrates CRS for antenna ports 0,1, 2, and 3 (indicated as R₀, R₁, R₂, and R₃, respectively), UE-RS forantenna port 5 (indicated as R₅), and CSI-RS for antenna port 15(indicated as R). FIG. 2B illustrates an example of various channelswithin a DL subframe of a frame. The physical control format indicatorchannel (PCFICH) is within symbol 0 of slot 0, and carries a controlformat indicator (CFI) that indicates whether the physical downlinkcontrol channel (PDCCH) occupies 1, 2, or 3 symbols (FIG. 2B illustratesa PDCCH that occupies 3 symbols). The PDCCH carries downlink controlinformation (DCI) within one or more control channel elements (CCEs),each CCE including nine RE groups (REGs), each REG including fourconsecutive REs in an OFDM symbol. A UE may be configured with aUE-specific enhanced PDCCH (ePDCCH) that also carries DCI. The ePDCCHmay have 2, 4, or 8 RB pairs (FIG. 2B shows two RB pairs, each subsetincluding one RB pair). The physical hybrid automatic repeat request(ARQ) (HARQ) indicator channel (PHICH) is also within symbol 0 of slot 0and carries the HARQ indicator (HI) that indicates HARQ acknowledgement(ACK)/negative ACK (NACK) feedback based on the physical uplink sharedchannel (PUSCH). The primary synchronization channel (PSCH) is withinsymbol 6 of slot 0 within subframes 0 and 5 of a frame, and carries aprimary synchronization signal (PSS) that is used by a UE to determinesubframe timing and a physical layer identity. The secondarysynchronization channel (SSCH) is within symbol 5 of slot 0 withinsubframes 0 and 5 of a frame, and carries a secondary synchronizationsignal (SSS) that is used by a UE to determine a physical layer cellidentity group number. Based on the physical layer identity and thephysical layer cell identity group number, the UE can determine aphysical cell identifier (PCI). Based on the PCI, the UE can determinethe locations of the aforementioned DL-RS. The physical broadcastchannel (PBCH) is within symbols 0, 1, 2, 3 of slot 1 of subframe 0 of aframe, and carries a master information block (MIB). The MIB provides anumber of RBs in the DL system bandwidth, a PHICH configuration, and asystem frame number (SFN). The physical downlink shared channel (PDSCH)carries user data, broadcast system information not transmitted throughthe PBCH such as system information blocks (SIBs), and paging messages.

As illustrated in FIG. 2C, some of the REs carry demodulation referencesignals (DM-RS) for channel estimation at the eNB. The UE mayadditionally transmit sounding reference signals (SRS) in the lastsymbol of a subframe. The SRS may have a comb structure, and a UE maytransmit SRS on one of the combs. The SRS may be used by an eNB forchannel quality estimation to enable frequency-dependent scheduling onthe UL. FIG. 2D illustrates an example of various channels within an ULsubframe of a frame. A physical random access channel (PRACH) may bewithin one or more subframes within a frame based on the PRACHconfiguration. The PRACH may include six consecutive RB pairs within asubframe. The PRACH allows the UE to perform initial system access andachieve UL synchronization. A physical uplink control channel (PUCCH)may be located on edges of the UL system bandwidth. The PUCCH carriesuplink control information (UCI), such as scheduling requests, a channelquality indicator (CQI), a precoding matrix indicator (PMI), a rankindicator (RI), and HARQ ACK/NACK feedback. The PUSCH carries data, andmay additionally be used to carry a buffer status report (BSR), a powerheadroom report (PHR), and/or UCI.

FIG. 3 is a block diagram of a base station 310 in communication with aUE 350 in an access network. In one aspect, the base station 310 may bea base station providing a macro cell, such as an eNB. In anotheraspect, the base station 310 may be a mmW base station. In yet anotheraspect, the base station 310 may include a mmW base station that isintegrated with another base station, such as a base station providing amacro cell. In the DL, IP packets from the EPC 160 may be provided to acontroller/processor 375. The controller/processor 375 implements layer3 and layer 2 functionality. Layer 3 includes a radio resource control(RRC) layer, and layer 2 includes a packet data convergence protocol(PDCP) layer, a radio link control (RLC) layer, and a medium accesscontrol (MAC) layer. The controller/processor 375 provides RRC layerfunctionality associated with broadcasting of system information (e.g.,MIB, SIBs), RRC connection control (e.g., RRC connection paging, RRCconnection establishment, RRC connection modification, and RRCconnection release), inter radio access technology (RAT) mobility, andmeasurement configuration for UE measurement reporting; PDCP layerfunctionality associated with header compression/decompression, security(ciphering, deciphering, integrity protection, integrity verification),and handover support functions; RLC layer functionality associated withthe transfer of upper layer packet data units (PDUs), error correctionthrough ARQ, concatenation, segmentation, and reassembly of RLC servicedata units (SDUs), re-segmentation of RLC data PDUs, and reordering ofRLC data PDUs; and MAC layer functionality associated with mappingbetween logical channels and transport channels, multiplexing of MACSDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs,scheduling information reporting, error correction through HARQ,priority handling, and logical channel prioritization.

The transmit (TX) processor 316 and the receive (RX) processor 370implement layer 1 functionality associated with various signalprocessing functions. Layer 1, which includes a physical (PHY) layer,may include error detection on the transport channels, forward errorcorrection (FEC) coding/decoding of the transport channels,interleaving, rate matching, mapping onto physical channels,modulation/demodulation of physical channels, and MIMO antennaprocessing. The TX processor 316 handles mapping to signalconstellations based on various modulation schemes (e.g., binaryphase-shift keying (BPSK), quadrature phase-shift keying (QPSK),M-phase-shift keying (M-PSK), M-quadrature amplitude modulation(M-QAM)). The coded and modulated symbols may then be split intoparallel streams. Each stream may then be mapped to an OFDM subcarrier,multiplexed with a reference signal (e.g., pilot) in the time and/orfrequency domain, and then combined together using an Inverse FastFourier Transform (IFFT) to produce a physical channel carrying a timedomain OFDM symbol stream. The OFDM stream is spatially precoded toproduce multiple spatial streams. Channel estimates from a channelestimator 374 may be used to determine the coding and modulation scheme,as well as for spatial processing. The channel estimate may be derivedfrom a reference signal and/or channel condition feedback transmitted bythe UE 350. Each spatial stream may then be provided to a differentantenna 320 via a separate transmitter 318TX. Each transmitter 318TX maymodulate an RF carrier with a respective spatial stream fortransmission.

At the UE 350, each receiver 354RX receives a signal through itsrespective antenna 352. Each receiver 354RX recovers informationmodulated onto an RF carrier and provides the information to the receive(RX) processor 356. The TX processor 368 and the RX processor 356implement layer 1 functionality associated with various signalprocessing functions. The RX processor 356 may perform spatialprocessing on the information to recover any spatial streams destinedfor the UE 350. If multiple spatial streams are destined for the UE 350,they may be combined by the RX processor 356 into a single OFDM symbolstream. The RX processor 356 then converts the OFDM symbol stream fromthe time-domain to the frequency domain using a Fast Fourier Transform(FFT). The frequency domain signal comprises a separate OFDM symbolstream for each subcarrier of the OFDM signal. The symbols on eachsubcarrier, and the reference signal, are recovered and demodulated bydetermining the most likely signal constellation points transmitted bythe base station 310. These soft decisions may be based on channelestimates computed by the channel estimator 358. The soft decisions arethen decoded and deinterleaved to recover the data and control signalsthat were originally transmitted by the base station 310 on the physicalchannel. The data and control signals are then provided to thecontroller/processor 359, which implements layer 3 and layer 2functionality.

The controller/processor 359 can be associated with a memory 360 thatstores program codes and data. The memory 360 may be referred to as acomputer-readable medium. In the UL, the controller/processor 359provides demultiplexing between transport and logical channels, packetreassembly, deciphering, header decompression, and control signalprocessing to recover IP packets from the EPC 160. Thecontroller/processor 359 is also responsible for error detection usingan ACK and/or NACK protocol to support HARQ operations.

Similar to the functionality described in connection with the DLtransmission by the base station 310, the controller/processor 359provides RRC layer functionality associated with system information(e.g., MIB, SIBs) acquisition, RRC connections, and measurementreporting; PDCP layer functionality associated with headercompression/decompression, and security (ciphering, deciphering,integrity protection, integrity verification); RLC layer functionalityassociated with the transfer of upper layer PDUs, error correctionthrough ARQ, concatenation, segmentation, and reassembly of RLC SDUs,re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; andMAC layer functionality associated with mapping between logical channelsand transport channels, multiplexing of MAC SDUs onto TBs,demultiplexing of MAC SDUs from TBs, scheduling information reporting,error correction through HARQ, priority handling, and logical channelprioritization.

Channel estimates derived by a channel estimator 358 from a referencesignal or feedback transmitted by the base station 310 may be used bythe TX processor 368 to select the appropriate coding and modulationschemes, and to facilitate spatial processing. The spatial streamsgenerated by the TX processor 368 may be provided to different antenna352 via separate transmitters 354TX. Each transmitter 354TX may modulatean RF carrier with a respective spatial stream for transmission.

The UL transmission is processed at the base station 310 in a mannersimilar to that described in connection with the receiver function atthe UE 350. Each receiver 318RX receives a signal through its respectiveantenna 320. Each receiver 318RX recovers information modulated onto anRF carrier and provides the information to a RX processor 370.

The controller/processor 375 can be associated with a memory 376 thatstores program codes and data. The memory 376 may be referred to as acomputer-readable medium. In the UL, the controller/processor 375provides demultiplexing between transport and logical channels, packetreassembly, deciphering, header decompression, control signal processingto recover IP packets from the UE 350. IP packets from thecontroller/processor 375 may be provided to the EPC 160. Thecontroller/processor 375 is also responsible for error detection usingan ACK and/or NACK protocol to support HARQ operations.

FIG. 4 is a diagram of a wireless communications system 400. Thewireless communications system 400 may include a plurality of basestations 402, 404, each configured to provide a respective cell 410,412. Each of the base stations 402, 404 may be configured to communicatewith one or more UEs 406 a, 406 b, 406 c, 406 d, 408 operating on therespective cells 410, 412.

In one aspect, the first base station 402 may be configured tocommunicate at least two types of traffic: a first type of traffic whichmay eMBB traffic and a second type of traffic which may be URLLCtraffic. In the illustrated aspect, the first base station 402 maycommunicate with a first UE 408 according to URLLC and, additionally,may communicate with a second UE 406 a according to eMBB. The secondbase station 404 may be configured to communicate with the third andfourth UEs 406 c, 406 d according to at least eMBB. According to one ormore 3GPP technical specifications, both URLLC and eMBB may be regardedas 5G technologies; that is, the 5G RAT may include URLLC technologiesand eMBB technologies.

In one aspect, the subframe structure used for both the first type oftraffic (e.g., eMBB) and the second type of traffic (e.g., URLLC) may besynchronized. For example, subframe boundaries for the first type oftraffic (e.g., eMBB) and the second type of traffic (e.g., URLLC) may besynchronized, and the first type of traffic and the second type oftraffic may have the same numerology (e.g., a reference numerology,which may be fourteen). Further, the subframe structure for both thefirst type of traffic and the second type of traffic may be the same,including a first portion for data or control information (e.g., twelvesymbols), a second portion being a gap (e.g., a one-symbol gap), and athird portion for carrying ACK/NACK information at the end of thesubframe structure (e.g., a one-symbol portion for carrying the UCBchannel). The second portion may occur between the first portion andthird portion in the synchronized subframe structure.

In an aspect, the base stations 402, 404 may be configured to use a newradio (NR) frame structure at least within a cyclic prefix (CP)overhead. The description of NR frame structure is to be regarded asillustrative, and the present disclosure comprehends other structures orarrangements in addition to those described herein.

In one aspect, the reference numerology for a subframe definition may befourteen (14). That is, the base stations 402, 404 may be configured tocommunicate during a subframe that includes fourteen symbols.

In an aspect, the NR frame structure may include slots of a durationthat is less than the reference numerology for a subframe (e.g., anumber of symbols per slot may be fewer than a number of symbols persubframe). In an aspect, an integer number of slots may fit within onesubframe duration (e.g., at least for subcarrier spacing that is largerthan or equal to the reference numerology). In an aspect, such a slotstructure may allow for control information at the beginning, end, orboth the beginning and end of a slot. The slot configuration may be onepossible scheduling unit observed by the one or more base stations 402,404.

In an aspect, the NR frame structure may include a subslotconfiguration, which may also be known as a “mini-slot” or anothernaming convention related to a transmission time interval (TTI). Thesubslot configuration may support a transmission time or interval thatis shorter than the reference numerology (as well as the slotnumerology). For example, the reference numerology for a subframe may befourteen, and the numerology for a subslot may be less than fourteen(and may be less than the slot numerology, as well). In one aspect, asubslot may be the smallest scheduling unit observed by one or more basestations 402, 404. In one aspect, the subslot configuration may indicatethat control information may occur at the beginning of a subslot, theend of a subslot, or both the beginning and the end of a subslot. In oneaspect, the slot structure and subslot structure may be merged. Inanother aspect, the slot configuration may be absent.

As indicated, the first base station 402 may communicate a second typeof data and/or control information associated with URLLC. In one aspect,URLLC data and/or control information may be predictable (e.g.,periodic), in which case at least one semi-static resource may bereserved for frequency-division multiplexing (FDM) or time-divisionmultiplexing (TDM) of URLLC content with eMBB information. In oneaspect, URLLC data and/or control information may be less predictable(e.g., sporadic), in which case the first base station 402 may beconfigured to puncture eMBB information with URLLC data and/or controlinformation. URLLC technologies may require packet delivery to occurwith stringent latency constraints and/or relatively low packet errorrate. Therefore, interference from other RATs due to coexistence mayhave detrimental consequences to the performance of URLLC. URLLC dataand/or control information may be prioritized over eMBB data and/orcontrol information and, therefore, the first base station 402 mayperform one or more operations in order to mitigate inter-cellinterference (e.g., interference caused by traffic in neighboring cells)and improve quality of URLLC applications.

The first base station 402 may be a neighbor of the second base station404. For example, the second base station 404 may be adjacent to thefirst base station 402. Consequently, the second base station 404 maycause interference to communication between the first UE 408 and thefirst base station 402. For example, the second base station 404 maycause interference to ACK/NACK information communicated by the first UE408 to the first base station 402 in response to downlink transmissionsfrom the first base station 402. Therefore, the communication betweenthe first base station 402 and the first UE 408 may benefit from one ormore operations by the second base station 404 that mitigate theinterference.

In various aspects, the first base station 402 may configure a subframewith a subslot configuration that includes a plurality of subslots. Eachsubslot may have a number of symbols (e.g., a duration) that is lessthan a number of symbols included in each subframe. Each subframe mayinclude a portion for carrying ACK/NACK information. In aspects, thefirst base station 402 may puncture, in at least two subslots includedin a subframe, a first type of data or control information (e.g., eMBBdata or control information) with a second type of data or controlinformation (e.g., URLLC data or control information). For example, thefirst base station 402 may puncture data or control informationassociated with eMBB carried in at least two subslots included in asubframe, with data or control information associated with URLLC. Inaspects, the first base station 402 may bundle the at least two subslotswithin a subframe, and the ACK/NACK portion of the subframe may be usedto carry ACK/NACK information associated with the second type of data orcontrol information carried in the bundled at least two subslots. In anaspect, the first base station 402 may communicate the second type ofdata or control information 420 with the first UE 408 during the bundledsubslots 198.

In aspects, the first UE 408 may receive the second type of data orcontrol information 420 during the at least two bundled subslots. Thefirst UE 408 may determine ACK/NACK information for the second type ofdata or control information 420 carried in the bundled subslots. Forexample, the first UE 408 may bundle ACK/NACK information 422 for thebundled subslots (e.g., the ACK/NACK information 422 may indicate anacknowledgement or negative acknowledgment for the second type of dataor control information 420 even through the second type of data orcontrol information may be carried in a plurality of subslots).

In one aspect, the first UE 408 may determine an ACK when the first UE408 is able to successfully decode the second type of data or controlinformation 420 carried in the bundled subslots. However, the first UE408 may determine a NACK when the first UE 408 is unable to successfullydecode the second type of data or control information 420 carried in thebundled subslots. The first UE 408 may then send the ACK/NACKinformation 422 during the portion of the subframe allocated forcarrying ACK/NACK information.

When the first base station 402 receives ACK/NACK information 422indicating a NACK associated with the second type of data or controlinformation 420 carried in the bundled subslots, the first base station402 may determine that the second type of data or control information420 is to be retransmitted to the first UE 408, for example, because thefirst UE 408 was unable to decode the second type of data or controlinformation 420 carried in the bundled subslots. Accordingly, the firstbase station 402 may reschedule the second type of data or controlinformation 420 and send the rescheduled second type of data or controlinformation 424 to the first UE 408, for example, in another subslot ofa subsequent frame. While the second type of data or control information420 may be carried in bundled subslots, the first base station 402 maysend the rescheduled second type of data or control information 424 inone subslot (e.g., the rescheduled second type of data or controlinformation 424 may be communicated using fewer symbols to carry thebits for the rescheduled second type of data or control information424).

While the ACK/NACK information 422 sent by the first UE 408 may beintended for the first base station 402, the second base station 404 mayalso receive the ACK/NACK information 422 from the first UE 408, forexample, due to the proximity of the second base station 404 to thefirst base station 402 and/or the first UE 408. In an aspect, the firstUE 408 may send the ACK/NACK information 422 on an UCB channel, whichmay also be known in some aspects as an eMBB UCB channel. Thus, whilethe second base station 404 may be configured to communicate accordingto the first type of data or control information (e.g., eMBB), theACK/NACK information 422 associated with the second type of data orcontrol information (e.g., URLLC) may be carried on a channel that thesecond base station 404 is configured to monitor.

Based on the reception of the ACK/NACK information 422, the second basestation 404 may be configured to reduce a transmission power for a firsttype of data or control information 442 (e.g., eMBB data or controlinformation) during a subsequent subframe (e.g., the next subframeimmediately following the subframe including the bundled subslots inwhich the second type of data or control information 420 istransmitted). For example, the ACK/NACK information 422 may indicate aNACK, and therefore the second base station 404 may reduce atransmission power (e.g., perform power fallback) during a subsequentsubframe in which the second base station 404 transmits the first typeof data or control information 442. According to one aspect, the secondbase station 404 may reduce a transmission power by selecting a secondtransmission power that is lower than a previously used transmissionpower. In another aspect, the second base station 404 may reduce atransmission power by reducing a previously used transmission power by apredetermined increment or percentage.

In one aspect, the first base station 402 may transmit the rescheduledsecond type of data or control information 424 contemporaneously withthe transmission of the first type of data or control information 442 bythe second base station 404. Therefore, the second base station 404 mayreduce a transmission power (e.g., perform power fallback) during thecontemporaneous transmission of the first type of data or controlinformation 442, which may mitigate interference to transmission of therescheduled second type of data or control information 424 by the firstbase station 402.

In another aspect, the second base station 404 may reduce transmissionpower by yielding transmission of the first type of data or controlinformation 442 (e.g., the second base station 404 may delaytransmission of the first type of data or control information 442 untilafter the first base station 402 transmits the rescheduled second typeof data or control information 424). For example, the second basestation 404 may yield transmission during a subframe immediatelyfollowing the subframe in which the ACK/NACK information 422 is carried.The second base station 404 may then transmit the first type of data orcontrol information 442 during a subframe that follows the subframeduring which the second base station 404 yielded transmission.

In order for the second base station 404 to detect the ACK/NACKinformation from the first UE 408, the first base station 402 may send,to the second base station 404, information 440 associated with theACK/NACK configuration. The first base station 402 may send theinformation 440 indicating the configuration using a backhaul link(e.g., via the X2 interface).

Accordingly, the first base station 402 may send, to the second basestation 404, information 440 indicating a configuration of the portionfor carrying the ACK/NACK information 422 associated with the secondtype of data or control information. The second base station 404 mayreceive this information 440 and, therefore, determine one or moreresources that the second base station 404 is to monitor in order todetect ACK/NACK information 422.

The information 440 indicating the configuration may include, forexample, an indication of one or more resources on which the ACK/NACKinformation 422 may be carried. For example, the first base station 402may indicate, to the second base station 404, information 440 indicatingone or more symbols during which the ACK/NACK information 422 may becarried (e.g., the last symbol of a subframe). In one aspect, the firstbase station 402 may send, to the second base station 404, information440 indicating a channel on which the ACK/NACK information is to becarried, such as an UCB channel.

In one aspect, the first base station 402 may transmit the rescheduledsecond type of data or control information 424 during a subslot thatdoes not consume an entire subframe. Therefore, the second base station404 may yield or perform power fallback during a portion of a subframe.The first base station 402 may then transmit the rescheduled second typeof data or control information 424 during the portion of the subframe inwhich the second base station reduces transmission power (e.g., thesubslot carrying the rescheduled second type of data or controlinformation 424 may occur contemporaneously with the portion of thesubframe during which the second base station 404 reduces transmissionpower).

FIG. 5 illustrates a subframe structure 500, according to an aspect. Thesubframe structure 500 may include a self-contained subframe 510. Thatis, the self-contained subframe 510 may include a portion 518 forcarrying ACK/NACK information. In an aspect, the ACK/NACK informationmay be carried on an UCB channel 522.

In aspects, a base station may communicate content in a URLLC cell 508during the self-contained subframe 510. When a URLLC packet 540 arrives(e.g., from a higher layer), the base station may puncture data orcontrol information associated with eMBB with URLLC data or controlinformation derived from the URLLC packet 540.

For example, the URLLC data or control information from the URLLC packet540 may be carried in two symbols of a URLLC portion 514 of theself-contained subframe 510. The corresponding ACK/NACK information 520for the URLLC content carried in the URLLC portion 514 may occur duringthe ACK/NACK portion 518 at the end of the self-contained subframe 510.

Because URLLC may adhere to low-latency and low-error rate requirements,the URLLC content may be punctured into the self-contained subframe 510as soon as the URLLC packet 540 arrives. Therefore, a first eMBB portion512 a may carry eMBB data or control information, and the URLLC portion514 may be punctured following the first eMBB portion 512 a (e.g.,according to when the URLLC packet 540 arrives). Because the URLLC dataor control information may be punctured into the eMBB data or controlinformation, an intervening eMBB portion 512 b may occur between theURLLC portion 514 and the ACK/NACK portion 518. In various aspects, agap 516 may additionally occur before the ACK/NACK information 520(e.g., for switching between uplink and downlink). This intervening eMBBportion 512 b and/or gap 516 may lead to a delay in communicatingACK/NACK information 520, for example, because of the intervening eMBBportion 512 b. Accordingly, a URLLC cell may benefit from a bundledsubslot configuration.

FIG. 6 illustrates a subslot configuration 600, according to an aspect.In an aspect, an eMBB/URLLC cell 602 (e.g., the first cell 410 providedby the first base station 402) may configure a subframe 608 with aself-contained subslot 620. The subslot 620 may be regarded as“self-contained” because the subslot 620 includes at least a firstportion 622 for carrying data or control information and a third portion626 for carrying ACK/NACK information associated with the first portion622 (n.b., the subslot 620 may include a second portion 624 that is agap between the first and third portions). That is, the self-containedsubslot 620 may include a portion 626 for carrying ACK/NACK information.The subframe 608 configured with the self-contained subslot 620 mayinclude a separate portion 616 for carrying a UCB channel, for example,after a gap 614 (e.g., for switching between downlink and uplink).

In aspects, a base station may communicate content in a eMBB/URLLC cell602 during the subframe 608. When a URLLC packet 640 arrives (e.g., froma higher layer), the base station may puncture data or controlinformation associated with eMBB with URLLC data or control informationderived from the URLLC packet 640. For example, the URLLC data orcontrol information from the URLLC packet 640 may be carried in twosymbols of a self-contained subslot 620. Because URLLC may adhere tolow-latency and low-error rate requirements, the URLLC content may bepunctured into the self-contained sub slot 620 as soon as the URLLCpacket 640 arrives. For example, for the subframe 608, a first eMBBportion 612 a may be mapped to the subframe, and data or controlinformation from the URLLC packet may be punctured in the subframe afterthe first eMBB portion 612 a, but before a second eMBB portion 612 b.Also after the first eMBB portion 612 a but before the second eMBBportion 612 b may be a second portion 624 (e.g., gap for switchingbetween downlink and uplink) and the portion 626 carrying the ACK/NACKinformation related to the first portion 622, thus forming theself-contained subslot 620.

In an eMBB cell 604, which may neighbor the eMBB/URLLC cell 602, data orcontrol information associated with eMBB may be communicated during asubframe 606 that overlaps with (e.g., occurs contemporaneously with)the self-contained subslot 620. This eMBB traffic during the eMBBsubframe 606 may cause interference 642 to the self-contained subslot620. For example, the interference 642 may prevent a base station fromreceiving and/or decoding ACK/NACK information associated with the firstportion 622 of the self-contained subslot 620. Accordingly, the URLLC(or URLCC/eMBB) cell may benefit when the subslot configuration of theURLLC cell is bundled and ACK/NACK information is carried on the UCBchannel 630. For example, ACK/NACK information in a URLLC cell butcarried on the UCB channel 630 may be received in the eMBB cell 604 andtransmission power may be reduced in the eMBB cell to mitigateinterference 642 during transmission of a subsequent subframe.

FIG. 7 illustrates a subslot configuration 700, according to an aspect.While FIG. 7 illustrates the configuration 700 in the context of eMBB asa first type of traffic and URLLC as a second type of traffic, thepresent disclosure comprehends different types of traffic, such asmachine-type communication (MTC), enhanced MTC, or another 5Gtechnology.

In various aspects, a subframe 710 may be configured in cell (e.g., thefirst cell 410, the eMBB/URLLC cell 602) based on a referencenumerology, such as fourteen. The subframe 710 may include a portion 718that is to carry data and/or control information and a portion 726 thatis to carry ACK/NACK information (e.g., on a UCB channel), with a gap724 occurring between the portion 718 in which data and/or controlinformation is carried and the portion 726 in which ACK/NACK informationis carried.

In various aspects, URLLC may require expeditious delivery. Therefore,when a URLLC packet arrives (e.g., from a higher layer), the URLLCinformation should be communicated as quickly as possible. In FIG. 7, aURLLC packet 740 may arrive (e.g., from a higher layer) and may bescheduled in a same subframe 710 during which the URLLC packet 740arrives.

In an aspect, data and/or control information determined from the URLLCpacket 740 may be punctured 742 by a base station into symbols of theportion 718 (e.g., carrying eMBB data or control information) in orderto quickly schedule URLLC data or control information. The URLLC data orcontrol information may then be carried in the subslots 722 a, 722 b,722 c, 722 d, which may be included in a bundle 720 during the subframe710). In one aspect, the bundle 720 may occupy a remainder of thesubframe after puncturing 742 begins (e.g., an intervening eMBB portion612 b may be absent). In other words, after puncturing 742, the bundle720 may occupy a remainder of the subframe until the gap 724. The bundle720 may improve reliability of communicating the data or controlinformation determined from the URLLC packet 740 within a hard latencybound.

For example, in the context of FIG. 4, the second type of data orcontrol information 420 may be determined from the URLLC packet 740. Thefirst base station 402 may include, in a bundle 720, a plurality ofsubslots 722 a, 722 b, 722 c, 722 d in which the second type of data orcontrol information 420 is to be carried. In one aspect, the subframe710 may carry eMBB data or control information and, therefore, the firstbase station 402 may puncture 742 the eMBB data or control informationwith the second type of data or control information 420 obtained fromthe URLLC packet 740. The base station 402 may then communicate thesecond type of data or control information 420 to the first UE 408during the subslots 722 a, 722 b, 722 c, 722 d included in the bundle720 within the subframe 710.

Further to such an example, the first UE 408 may receive the second typeof data or control information 420 during the subslots 722 a, 722 b, 722c, 722 d included in the bundle 720 within the subframe 710. The firstUE 408 may determine ACK/NACK information 730 (e.g., ACK/NACKinformation 422) for the second type of data or control information 420.The first UE 408 may then send the ACK/NACK information 730 (e.g.,ACK/NACK information 422) during the portion 726 of the subframe 710 forcarrying ACK/NACK information. In an aspect, the ACK/NACK information730 (e.g., ACK/NACK information 422) may be carried on an UCB channel.

While the subslot configuration 700 illustrates a plurality of subslots722 a, 722 b, 722 c, 722 d each having two OFDM symbols, otherconfigurations are possible without departing from the presentdisclosure. For example, a first subslot 722 a may include two symbols,whereas a second subslot 722 b may include four symbols. In one aspect,a bundle 720 of subslots 722 a, 722 b, 722 c, 722 d that contains Ntotal symbols (e.g., two, four, eight, etc.) may be equivalentlyreplaced by an N-symbol subslot. For example, a bundle 720 of fourtwo-symbol subslots 722 a, 722 b, 722 c, 722 d may be equivalent to asingle eight-symbol subslot.

FIG. 8 is a diagram of a subslot configuration 800, according to variousaspects. While FIG. 8 illustrates the configuration 800 in the contextof eMBB as a first type of traffic and URLLC as a second type oftraffic, the present disclosure comprehends different types of traffic,such as MTC, enhanced MTC, or another 5G technology.

In one aspect, a subframe structure used for a first cell (e.g., aURLLC/eMBB cell 802) and a second cell (e.g., the eMBB cell 804) may besynchronized. For example, subframe boundaries for the first type oftraffic (e.g., eMBB) and the second type of traffic (e.g., URLLC) may besynchronized, and the first type of traffic and the second type oftraffic may have the same numerology (e.g., a reference numerology,which may be fourteen). In one aspect, a first base station (e.g.,providing the URLLC/eMBB cell 802) may provide information on subframetiming (e.g., boundaries) to another base station (e.g., providing theeMBB cell 804) so that the other base station may synchronize subframeboundaries with the first base station. For example, the first basestation may send information on subframe timing (e.g., boundaries) overan X2 interface.

The subframe structure for the URLLC/eMBB cell 802 may include a firstportion 818 (e.g., twelve symbols) for carrying data or controlinformation, and a third portion 832 (e.g., one symbol) for carryingACK/NACK information, and a gap 824 (e.g., one symbol) may occur betweenthe first portion 818 and the third portion 832. Similarly, the subframestructure for the eMBB cell 804 may include a first portion 806 a (e.g.,twelve symbols) for carrying data or control information and a thirdportion 834 (e.g., one symbol) for carrying ACK/NACK information, and agap 826 (e.g., one symbol) may occur between the first portion 806 a andthe third portion 834.

In various aspects, the respective first portions 818, 806 a may beconfigured in a respective cell 802, 804 based on a referencenumerology, such as fourteen. Based on the synchronization, the firstportion 818 in the URLLC/eMBB cell 802 may occur contemporaneously withthe first portion 806 a in the eMBB cell 804 during the subframe t 810.For example, each of the first portions 818, 806 a may be twelvesymbols. Similarly, the third portion 832 in the URLLC/eMBB cell 802 mayoccur contemporaneously with the third portion 834 in the eMBB cell 804during the subframe t 810, with respective gaps 824, 826 occurringbetween respective first portions 818, 806 a and third portions 832,834.

In various aspects, URLLC applications may require expeditious delivery.Therefore, when a URLLC packet arrives (e.g., from a higher layer), theURLLC information should be communicated as quickly as possible. In FIG.8, a URLLC packet 840 may arrive (e.g., from a higher layer) and may bescheduled in a same subframe t 810 during which the URLLC packet 840arrives.

In an aspect, data and/or control information determined from the URLLCpacket 840 may be punctured into symbols of the first portion 818 in theURLLC/eMBB cell 802 in order to quickly schedule URLLC data or controlinformation. The URLLC data or control information may then be carriedin bundled subslots 820 during the subframe t 810. In one aspect, thebundle 820 may occupy a remainder of the subframe after puncturingbegins (e.g., after puncturing the bundled subslots 820 may occupy thesubframe t 810 until the gap 824).

In various aspects, a first base station (e.g., the first base station402) may be punctured into symbols of the first portion 818 during thebundled subslots 810, for example, after a four-symbol eMBB portion(e.g., the bundled subslots 820 may occupy the remaining eight symbolsof the first portion 818). URLLC data or control information, determinedfrom the URLLC packet 840, may then be communicated to a UE (e.g., thefirst UE 408) during the bundled subslots 820 of the subframe t 810.

The UE may receive the URLLC data or control information carried in thebundled subslots 820 and attempt to decode the URLLC data or controlinformation. In an aspect, the UE may be unable to successfully decodethe URLLC data or control information carried in the bundled subslots820 and, therefore, may determine a NACK 830 in order to indicate thatthe UE is unable to decode the URLLC data or control information carriedin the bundled subslots 820. The UE may then send the NACK 830 duringthe third portion 832, and the NACK may be carried on a UCB channel 860.

The NACK 830 may be received in both the URLLC/eMBB cell 802 and theeMBB cell 804. In the URLLC/eMBB cell 802, a first base station (e.g.,the first base station 402) may determine, based on the NACK 830, thatthe URLLC data or control information carried in the bundled subslots820 is to be rescheduled. Accordingly, the first base station mayreschedule the URLLC data or control information in at least one subslot850 of the subframe t+1 812. In an aspect, the URLLC data or controlinformation may be carried in the bundled subslots 820, but may berescheduled during one subslot 850, for example, because a same numberof bits indicating the URLLC data or control information may be carriedin the subslot 850 using a different coding rate.

In the eMBB cell 804, a second base station (e.g., the second basestation 404) may determine, based on the NACK 830, that the second basestation is to reduce transmission power during at least a first portion806 b of the subframe t+1 812, for example, in order to mitigateinterference to the URLLC data or control information communicated tothe UE. Accordingly, the second base station may reduce transmissionpower (e.g., perform power fallback or yield transmission) during afirst portion 806 b of the subframe t+1 812.

The first base station may then transmit the rescheduled URLLC data orcontrol information (e.g., the rescheduled second type of data orcontrol information 424) during the subslot 850 of the subframe t+1 812.Because the second base station may perform power fallback during thefirst portion 806 b of the subframe t+1 812, the UE may be able tosuccessfully decode the rescheduled URLLC data or control information.In one aspect, URLLC applications in the URLLC/eMBB cell 802 may bebudgeted a delay period (e.g., 500 microseconds), for example, so thatthe URLLC data or control information still adheres to the latencyrequirements of URLLC.

FIG. 9 is a flowchart of a method 900 of wireless communication. Themethod may be performed by a base station (e.g., the base station 102,the base station 402, the apparatus 1002/1002′). While the method 900illustrates a plurality of discrete operations, the present disclosurecontemplates aspects in which one or more operations are transposed,omitted, and/or contemporaneously performed.

Beginning first with operation 902, the base station may send, to aneighboring base station, information indicating a configuration of aportion for carrying ACK/NACK information associated with a second typeof data or control information. The configuration information mayinclude one or more resources on which ACK/NACK information associatedwith the second type of data or control information is to be carried. Inone aspect, the second type of data or control information may be URLLCdata or control information. In the context of FIG. 4, the first basestation 402 may send, to the second base station 404, information 440indicating a configuration of a portion for carrying ACK/NACKinformation, for example, so that the second base station 404 maymonitor for and detect the ACK/NACK information 422.

At operation 904, the base station may puncture, in at least twosubslots, a first type of data or control information with a second typeof data or control information. For example, the base station may mapthe first type of data or control information to one or more resources(e.g., RBs), but at least a portion of the bits of those resources maybe used to carry the second type of data or control information—e.g.,the base station may map the second type of data or control informationover the first type of data or control information in one or moreresources. In an aspect, the first type of data or control informationmay be eMBB data or control information, and the second type of data orcontrol information may be URLLC data or control information. In thecontext of FIG. 4, the first base station 402 may puncture a first typeof data or control information with a second type of data or controlinformation 420. For example, the first base station 402 may puncture742 the first portion 718 of a subframe 710 with the second type of dataor control information determined from the URLLC packet 740. In anotherexample, the first base station 402 may puncture the first portion 818of a subframe t 810 with URLLC data or control information determinedfrom the URLLC packet 840.

At operation 906, the base station may bundle the at least two subslotswithin a subframe. For example, the base station may include the secondtype of data or control information in a first sub slot, and may alsoinclude the second type of data or control information in a secondsubslot. The second type of data or control information in the secondsubslot may be a redundancy version of the second type of data orcontrol information in the first subslot. The base station may theninclude both of these subslots in a subframe, for example, with thesecond subslot immediately following the first subslot (e.g., nointervening portions). In an aspect, the subframe may include a portionfor carrying ACK/NACK information associated with the second type ofdata or control information. In the context of FIG. 4, the first basestation 402 may bundle at least two subslots in which the second type ofdata or control information 420 is punctured. For example, the firstbase station 402 may bundle the subslots 722 a, 722 b, 722 c, 722 dwithin the subframe 710. In another example, the second type of data orcontrol information may be carried in the bundled subslots 820.

At operation 908, the base station may communicate with a UE during theat least two subslots bundled within the subframe. For example, the basestation may transmit the second type of data or control information inthe bundled at least two subslots within the subframe. In the context ofFIG. 4, the first base station 402 may transmit the second type of dataor control information 420 during at least two subslots bundled within asubframe. For example, the first base station 402 may transmit thesecond type of data or control information 420 during the bundle 720. Inanother example, the first base station 402 may transmit the second typeof data or control information 420 during the bundled subslots 820.

At operation 910, the base station may receive, from the UE, ACK/NACKinformation associated with the second type of data or controlinformation carried in the bundled at least two subslots. In one aspect,the ACK/NACK information may be carried on an UCB channel. In thecontext of FIG. 4, the first base station 402 may receive, from thefirst UE 408, ACK/NACK information 422. For example, the first basestation 402 may receive ACK/NACK information 730 carried in the portion726 at the end of the subframe 710. In another example, the first basestation 402 may receive ACK/NACK information that is a NACK 830 carriedon an UCB channel 860.

If the ACK/NACK information indicates an acknowledgement, then the basestation may continue to further communicate with the UE, for example,because the UE successfully decoded the second type of data or controlinformation. However, if the ACK/NACK information indicates a negativeacknowledgement, then the method 900 may proceed to operation 912. Atoperation 912, the base station may reschedule the second type of dataor control information. For example, the base station may determine asubsequent time (e.g., a subsequent subframe) for sending the secondtype of data or control information, and the base station may map thesecond type of data or control information to resources corresponding tothat subsequent time. In the context of FIG. 4, the first base station402 may reschedule the second type of data or control information 424.For example, the first base station 402 may reschedule URLLC data orcontrol information, determined from the URLLC packet 840, during the atleast one subslot 850.

At operation 914, the base station may send the rescheduled second typeof data or control information. In the context of FIG. 4, the first basestation 402 may send the rescheduled second type of data or controlinformation 424. For example, the first base station 402 may send URLLCdata or control information, determined from the URLLC packet 840,during the at least one subslot 850.

FIG. 10 is a flowchart of a method 1000 of wireless communication. Themethod may be performed by a base station (e.g., the base station 180,the base station 404, the apparatus 1402/1402′). While the method 1000illustrates a plurality of discrete operations, the present disclosurecontemplates aspects in which one or more operations are transposed,omitted, and/or contemporaneously performed.

Beginning first with operation 1002, the base station may receive, froma neighboring base station, information indicating a configuration of aportion for carrying ACK/NACK information associated with a second typeof data or control information. The configuration information mayinclude one or more resources on which ACK/NACK information associatedwith the second type of data or control information is to be carried(e.g., a last symbol of subframe, a UCB channel). In one aspect, thesecond type of data or control information may be URLLC data or controlinformation. In the context of FIG. 4, the second base station 404 mayreceive, from the first base station 402, information 440 indicating aconfiguration of a portion for carrying ACK/NACK information, forexample, so that the second base station 404 may monitor for and detectthe ACK/NACK information 422.

At operation 1004, the base station may receive, from a UE, ACK/NACKinformation associated with the second type of data or controlinformation, e.g., based on the received configuration information. Inone aspect, the ACK/NACK information may be carried on an UCB channel.In the context of FIG. 4, the second base station 404 may receive, fromthe first UE 408, ACK/NACK information 422. For example, the second basestation 404 may receive ACK/NACK information that is a NACK 830 carriedon an UCB channel 860.

If the ACK/NACK information indicates an acknowledgement (or if noACK/NACK information is detected), then the base station may continue tofurther communicate with other UE(s) operating on a cell provided by thebase station UE, for example, because the base station has not receivedan indication that the base station is causing interference to aneighboring cell. However, if the ACK/NACK information indicates anegative acknowledgement, then the method 1000 may proceed to operation1006.

At operation 1006, the base station may reduce a transmission power fora first type of data or control information during a subsequentsubframe. For example, the base station may select or compute a reducedtransmission power that is relatively less than a previously usedtransmission power, and the base station may use the reducedtransmission power for transmission. The first type of data or controlinformation may be eMBB data or control information. In the context ofFIG. 4, the second base station 404 may reduce a transmission power fora first type of data or control information 442. For example, the secondbase station 404 may reduce a transmission power during a first portion806 b of the subframe t+1 812.

In one aspect, operation 1006 may include operation 1008. At operation1008, the base station may yield transmission of the first type of dataor control information during the subsequent subframe. In an aspect, thebase station may yield transmission by refraining from transmitting dataor control information (e.g., data or control information that wasotherwise scheduled for transmission). For example, the base station mayschedule transmission of the first type of data or control informationon one or more resources of the subsequent subframe, and then the basestation may refraining from sending the scheduled first type of data orcontrol information on the one or more resources of the subsequentsubframe. For example, the second base station 404 may yieldtransmission of a first type of data or control information 442 untilafter transmission of the rescheduled second type of data or controlinformation 424. For example, the second base station 404 may yieldtransmission during a first portion 806 b of the subframe t+1 812.

FIG. 11 is a flowchart of a method 1100 of wireless communication. Themethod may be performed by a UE (e.g., the UE 104, the first UE 408, theapparatus 1602/1602′). While the method 1100 illustrates a plurality ofdiscrete operations, the present disclosure contemplates aspects inwhich one or more operations are transposed, omitted, and/orcontemporaneously performed.

At operation 1102, the UE may receive, from a base station, a secondtype of data or control information carried in at least two subslotsbundled within a subframe. In an aspect, the second type of data orcontrol information is punctured into a first type of data or controlinformation. In an aspect, the subframe includes a portion for carryingACK/NACK information associated with the second type of data or controlinformation. The first type of data or control information may be eMBBdata or control information, and the second type of data or controlinformation may be URLLC data or control information.

In the context of FIG. 4, the first UE 408 may receive the second typeof data or control information 420. For example, the first UE 408 mayreceive the second type of data or control information that is punctured742 into symbols of the first portion 718 of a subframe 710. In anotherexample, the first UE 408 may receive the second type of data or controlinformation that is punctured into symbols of the first portion 818 of asubframe t 810. The first UE 408 may receive the second type of data orcontrol information carried in the subslots 722 a, 722 b, 722 c, 722 dof the bundle 720. In another example, the second type of data orcontrol information may be carried in the bundled subslots 820.

At operation 1104, the UE may determine ACK/NACK information for thesecond type of data or control information carried in the bundled atleast two subslots. For example, the UE may attempt to decode the secondtype of data or control information. If the UE successfully decodes thesecond type of data or control information, then the UE may generate ACKfeedback to indicate the successful reception and decoding of the secondtype of data or control information. However, if the UE is unsuccessfulin decoding the second type of data or control information, then the UEmay generate NACK feedback to indicate the failure in reception and/ordecoding of the second type of data or control information. In thecontext of FIG. 4, the first UE 408 may determine the ACK/NACKinformation 422 for the second type of data or control information 420.For example, the first UE 408 may determine the ACK/NACK information 730for URLLC data or control information carried in the bundle 720. Inanother example, the first UE 408 may determine the NACK 830 when thefirst UE 408 is unable to successfully decode the URLLC data or controlinformation carried in the bundled subslots 820.

At operation 1106, the UE may send the ACK/NACK information during theportion of the subframe for carrying ACK/NACK information. In an aspect,the ACK/NACK information may be carried on a UCB channel. In the contextof FIG. 4, the first UE 408 may send the ACK/NACK information 422, whichmay be received by both the first base station 402 and the second basestation 404. For example, the first UE 408 may send the ACK/NACKinformation 730 in the portion 726 of the subframe 710 for carryingACK/NACK information. In another example, the first UE 408 may send theNACK 830, which may be received in both the URLLC/eMBB cell 802 and theeMBB cell 804.

If the UE sends a NACK, the method 1100 may proceed to operation 1108.At operation 1108, the UE may receive a rescheduled second type of dataor control information. In the context of FIG. 4, the first UE 408 mayreceive the rescheduled second type of data or control information 424.For example, the first UE 408 may receive the rescheduled second type ofdata or control information carried in the at least one subslot 850 ofthe subframe t+1 812.

FIG. 12 is a conceptual data flow diagram 1200 illustrating the dataflow between different means/components in an exemplary apparatus 1202.The apparatus may be a base station.

The apparatus 1202 may include a reception component 1204 configured toreceive signals (e.g., from a UE 1250 and/or from a neighboring basestation 1260). The apparatus 1202 may include a transmission component1210 configured to transmit signals (e.g., to the UE 1250 and/or to aneighboring base station 1260).

The apparatus 1202 may include a content component 1208 configured todetermine content that is to be delivered to the UE 1250. The contentmay include URLLC data or control information. The content component1208 may provide the content to the scheduling component 1206. Thescheduling component 1206 may puncturing, in at least two subslots, afirst type of data or control information (e.g., eMBB data or controlinformation) with the content, which may be a second type of data orcontrol information (e.g., URLLC data or control information). In anaspect, the scheduling component 1206 may bundling the at least twosubslots within a subframe. In an aspect, the subframe may include aportion for carrying ACK/NACK information associated with the secondtype of data or control information. The transmission component 1210 maythen communicate with the UE 1250 during the at least two sub slotsbundled within the subframe.

In an aspect, the scheduling component 1206 may receive, from the UE1250, ACK/NACK information associated with the content, which may becarried on a UCB channel. If the ACK/NACK information indicates anegative acknowledgement by the UE 1250, the scheduling component 1206may reschedule the content (e.g., during a subslot of a next subframe).The transmission component 1210 may then send the rescheduled secondtype of data or control information to the UE 1250.

In an aspect, the apparatus 1202 may include a synchronization component1212. The synchronization component 1212 may be configured to determineinformation indicating a configuration of a portion for carryingACK/NACK information associated with a second type of data or controlinformation. The configuration information may include one or moreresources on which ACK/NACK information associated with the second typeof data or control information is to be carried (e.g., a last symbol ofsubframe, a UCB channel). The transmission component 1210 may thentransmit, to the neighboring base station 1260, information indicating aconfiguration of a portion for carrying ACK/NACK information, forexample, so that the neighboring base station may monitor for and detectthe ACK/NACK information from the UE 1250.

The apparatus may include additional components that perform each of theblocks of the algorithm in the aforementioned flowcharts of FIG. 9. Assuch, each block in the aforementioned flowcharts of FIG. 9 may beperformed by a component and the apparatus may include one or more ofthose components. The components may be one or more hardware componentsspecifically configured to carry out the stated processes/algorithm,implemented by a processor configured to perform the statedprocesses/algorithm, stored within a computer-readable medium forimplementation by a processor, or some combination thereof.

FIG. 13 is a diagram 1300 illustrating an example of a hardwareimplementation for an apparatus 1202′ employing a processing system1314. The processing system 1314 may be implemented with a busarchitecture, represented generally by the bus 1324. The bus 1324 mayinclude any number of interconnecting buses and bridges depending on thespecific application of the processing system 1314 and the overalldesign constraints. The bus 1324 links together various circuitsincluding one or more processors and/or hardware components, representedby the processor 1304, the components 1204, 1206, 1208, 1210, 1212 andthe computer-readable medium/memory 1306. The bus 1324 may also linkvarious other circuits such as timing sources, peripherals, voltageregulators, and power management circuits, which are well known in theart, and therefore, will not be described any further.

The processing system 1314 may be coupled to a transceiver 1310. Thetransceiver 1310 is coupled to one or more antennas 1320. Thetransceiver 1310 provides a means for communicating with various otherapparatus over a transmission medium. The transceiver 1310 receives asignal from the one or more antennas 1320, extracts information from thereceived signal, and provides the extracted information to theprocessing system 1314, specifically the reception component 1204. Inaddition, the transceiver 1310 receives information from the processingsystem 1314, specifically the transmission component 1210, and based onthe received information, generates a signal to be applied to the one ormore antennas 1320. The processing system 1314 includes a processor 1304coupled to a computer-readable medium/memory 1306. The processor 1304 isresponsible for general processing, including the execution of softwarestored on the computer-readable medium/memory 1306. The software, whenexecuted by the processor 1304, causes the processing system 1314 toperform the various functions described supra for any particularapparatus. The computer-readable medium/memory 1306 may also be used forstoring data that is manipulated by the processor 1304 when executingsoftware. The processing system 1314 further includes at least one ofthe components 1204, 1206, 1208, 1210, 1212. The components may besoftware components running in the processor 1304, resident/stored inthe computer readable medium/memory 1306, one or more hardwarecomponents coupled to the processor 1304, or some combination thereof.The processing system 1314 may be a component of the base station 310and may include the memory 376 and/or at least one of the TX processor316, the RX processor 370, and the controller/processor 375.

In one configuration, the apparatus 1202/1202′ for wirelesscommunication includes means for puncturing, in at least two subslots, afirst type of data or control information with a second type of data orcontrol information. The apparatus 1202/1202′ may further include meansfor bundling the at least two subslots within a subframe, wherein thesubframe includes a portion for carrying ACK/NACK information associatedwith the second type of data or control information. The apparatus1202/1202′ may further include means for communicating with a userequipment (UE) during the at least two subslots bundled within thesubframe.

The apparatus 1202/1202′ may further include means for receivingACK/NACK information associated with the second type of data or controlinformation carried in the bundled at least two subslots. In an aspect,wherein the ACK/NACK information is carried on an eMBB uplink commonburst channel. The apparatus 1202/1202′ may further include means forrescheduling the second type of data or control information when theACK/NACK information indicates a negative acknowledgement. The apparatus1202/1202′ may further include means for sending the rescheduled secondtype of data or control information. The apparatus 1202/1202′ mayfurther include means for sending, to a neighboring base station,information indicating a configuration of the portion for carryingACK/NACK information associated with the second type of data or controlinformation. In an aspect, the first type of data is associated witheMBB and the second type of data is associated with URLLC.

The aforementioned means may be one or more of the aforementionedcomponents of the apparatus 1202 and/or the processing system 1314 ofthe apparatus 1202′ configured to perform the functions recited by theaforementioned means. As described supra, the processing system 1314 mayinclude the TX Processor 316, the RX Processor 370, and thecontroller/processor 375. As such, in one configuration, theaforementioned means may be the TX Processor 316, the RX Processor 370,and the controller/processor 375 configured to perform the functionsrecited by the aforementioned means.

FIG. 14 is a conceptual data flow diagram 1400 illustrating the dataflow between different means/components in an exemplary apparatus 1402.The apparatus may be a base station.

The apparatus 1402 may include a reception component 1404 configured toreceive signals (e.g., from a first UE 1450, a second UE 1470, and/orfrom a neighboring base station 1460). The apparatus 1402 may include atransmission component 1410 configured to transmit signals (e.g., to thesecond UE 1470 and/or to a neighboring base station 1460).

In an aspect, the apparatus 1202 may include a synchronization component1408. The synchronization component 1408 may be configured to determineinformation indicating a configuration of a portion for carryingACK/NACK information associated with a second type of data or controlinformation, which may be received from the neighboring base station1460. The configuration information may include one or more resources onwhich ACK/NACK information associated with the second type of data orcontrol information is to be carried (e.g., a last symbol of subframe, aUCB channel).

The synchronization component 1408 may provide the configurationinformation to an ACK/NACK component 1406. Based on this configurationinformation, the ACK/NACK component 1406 may monitor for and detect theACK/NACK information from the UE 1450. In an aspect, the ACK/NACKinformation may be carried on a UCB channel; however, the ACK/NACKinformation may be associated with a second type of data or controlinformation (e.g., URLLC), while the apparatus 1402 is configured tocommunicate according to a first type of data or control information(e.g., eMBB).

When the ACK/NACK component 1406 detects a NACK from the first UE 1450,the ACK/NACK component 1406 may provide an indication of the NACK to thepower component 1412. The power component 1412 may be configured toreduce a transmission power for a first type of data or controlinformation during a subsequent subframe, for example, whencommunicating with the second UE 1470. In an aspect, the power component1412 may reduce the transmission power by causing the transmissioncomponent 1410 to yield transmission of the first type of data orcontrol information during the subsequent subframe.

The apparatus may include additional components that perform each of theblocks of the algorithm in the aforementioned flowcharts of FIG. 10. Assuch, each block in the aforementioned flowcharts of FIG. 10 may beperformed by a component and the apparatus may include one or more ofthose components. The components may be one or more hardware componentsspecifically configured to carry out the stated processes/algorithm,implemented by a processor configured to perform the statedprocesses/algorithm, stored within a computer-readable medium forimplementation by a processor, or some combination thereof.

FIG. 15 is a diagram 1500 illustrating an example of a hardwareimplementation for an apparatus 1402′ employing a processing system1514. The processing system 1514 may be implemented with a busarchitecture, represented generally by the bus 1524. The bus 1524 mayinclude any number of interconnecting buses and bridges depending on thespecific application of the processing system 1514 and the overalldesign constraints. The bus 1524 links together various circuitsincluding one or more processors and/or hardware components, representedby the processor 1504, the components 1404, 1406, 1408, 1410, 1412 andthe computer-readable medium/memory 1506. The bus 1524 may also linkvarious other circuits such as timing sources, peripherals, voltageregulators, and power management circuits, which are well known in theart, and therefore, will not be described any further.

The processing system 1514 may be coupled to a transceiver 1510. Thetransceiver 1510 is coupled to one or more antennas 1520. Thetransceiver 1510 provides a means for communicating with various otherapparatus over a transmission medium. The transceiver 1510 receives asignal from the one or more antennas 1520, extracts information from thereceived signal, and provides the extracted information to theprocessing system 1514, specifically the reception component 1404. Inaddition, the transceiver 1510 receives information from the processingsystem 1514, specifically the transmission component 1410, and based onthe received information, generates a signal to be applied to the one ormore antennas 1520. The processing system 1514 includes a processor 1504coupled to a computer-readable medium/memory 1506. The processor 1504 isresponsible for general processing, including the execution of softwarestored on the computer-readable medium/memory 1506. The software, whenexecuted by the processor 1504, causes the processing system 1514 toperform the various functions described supra for any particularapparatus. The computer-readable medium/memory 1506 may also be used forstoring data that is manipulated by the processor 1504 when executingsoftware. The processing system 1514 further includes at least one ofthe components 1404, 1406, 1408, 1410, 1412. The components may besoftware components running in the processor 1504, resident/stored inthe computer readable medium/memory 1506, one or more hardwarecomponents coupled to the processor 1504, or some combination thereof.The processing system 1514 may be a component of the base station 310and may include the memory 376 and/or at least one of the TX processor316, the RX processor 370, and the controller/processor 375.

In one configuration, the apparatus 1402/1402′ for wirelesscommunication includes means for receiving ACK/NACK informationassociated with a second type of data or control information. Theapparatus 1402/1402′ may further include means for reducing atransmission power for a first type of data or control informationduring a subsequent subframe when the ACK/NACK information indicates anegative acknowledgement. In an aspect, the means for reducing thetransmission power is configured to yield transmission of the first typeof data or control information during the subsequent subframe.

The apparatus 1402/1402′ may further include means for receiving, from aneighboring base station, information indicating a configuration of aportion of a subframe for carrying the ACK/NACK information. In anaspect, the ACK/NACK information is carried on an eMBB uplink commonburst channel. In an aspect, the first type of data is associated witheMBB and the second type of data is associated with URLLC).

The aforementioned means may be one or more of the aforementionedcomponents of the apparatus 1402 and/or the processing system 1514 ofthe apparatus 1402′ configured to perform the functions recited by theaforementioned means. As described supra, the processing system 1514 mayinclude the TX Processor 316, the RX Processor 370, and thecontroller/processor 375. As such, in one configuration, theaforementioned means may be the TX Processor 316, the RX Processor 370,and the controller/processor 375 configured to perform the functionsrecited by the aforementioned means.

FIG. 16 is a conceptual data flow diagram 1600 illustrating the dataflow between different means/components in an exemplary apparatus 1602.The apparatus may be a UE.

The apparatus 1602 may include a reception component 1604 configured toreceive signals (e.g., from a first base station 1650). The apparatus1402 may include a transmission component 1410 configured to transmitsignals (e.g., to the first base station 1650, although such signals maybe detected by a neighboring base station 1660).

In an aspect, the apparatus 1602 may include a content component 1606.The content component 1606 may be configured to receive content (e.g.,URLLC data or control information) from the first base station 1650, andthe content may be carried in bundled subslots of a subframe. In anaspect, the data or control information may be of a second type (e.g.,URLLC), and may be punctured, in at least two subslots bundled within asubframe, into a first type of data or control information (e.g., eMBBdata or control information). In an aspect, the subframe may include aportion for carrying ACK/NACK information associated with the secondtype of data or control information.

The content component 1606 may attempt to decode the second type of dataor control information received from the first base station 1650 andprovide an indication of whether the decoding was successful to anACK/NACK component 1608. The ACK/NACK component 1608 may determineACK/NACK information for the bundled subslots in which the second typeof data or control information is carried. For example, the ACK/NACKcomponent 1608 may determine an ACK when the content component 1606successfully decodes the second type of data or control informationcarried in the bundled subslots, and may determine a NACK otherwise.

The transmission component 1610 may transmit the determined ACK/NACKinformation in the portion of the subframe for carrying ACK/NACKinformation. The ACK/NACK information may be carried on a UCB channel.While the ACK/NACK information may be intended for the first basestation 1650, the neighboring base station 1660 may detect the ACK/NACKinformation.

If the ACK/NACK component 1608 causes transmission of a NACK, thecontent component 1606 may receive the second type of data or controlinformation during a rescheduled sub slot, which may occur during thenext subframe immediately after the subframe in which the bundledsubslots are carried.

The apparatus may include additional components that perform each of theblocks of the algorithm in the aforementioned flowcharts of FIG. 11. Assuch, each block in the aforementioned flowcharts of FIG. 11 may beperformed by a component and the apparatus may include one or more ofthose components. The components may be one or more hardware componentsspecifically configured to carry out the stated processes/algorithm,implemented by a processor configured to perform the statedprocesses/algorithm, stored within a computer-readable medium forimplementation by a processor, or some combination thereof.

FIG. 17 is a diagram 1700 illustrating an example of a hardwareimplementation for an apparatus 1602′ employing a processing system1714. The processing system 1714 may be implemented with a busarchitecture, represented generally by the bus 1724. The bus 1724 mayinclude any number of interconnecting buses and bridges depending on thespecific application of the processing system 1714 and the overalldesign constraints. The bus 1724 links together various circuitsincluding one or more processors and/or hardware components, representedby the processor 1704, the components 1604, 1606, 1608, 1610, 1612 andthe computer-readable medium/memory 1706. The bus 1724 may also linkvarious other circuits such as timing sources, peripherals, voltageregulators, and power management circuits, which are well known in theart, and therefore, will not be described any further.

The processing system 1714 may be coupled to a transceiver 1710. Thetransceiver 1710 is coupled to one or more antennas 1720. Thetransceiver 1710 provides a means for communicating with various otherapparatus over a transmission medium. The transceiver 1710 receives asignal from the one or more antennas 1720, extracts information from thereceived signal, and provides the extracted information to theprocessing system 1714, specifically the reception component 1604. Inaddition, the transceiver 1710 receives information from the processingsystem 1714, specifically the transmission component 1610, and based onthe received information, generates a signal to be applied to the one ormore antennas 1720. The processing system 1714 includes a processor 1704coupled to a computer-readable medium/memory 1706. The processor 1704 isresponsible for general processing, including the execution of softwarestored on the computer-readable medium/memory 1706. The software, whenexecuted by the processor 1704, causes the processing system 1714 toperform the various functions described supra for any particularapparatus. The computer-readable medium/memory 1706 may also be used forstoring data that is manipulated by the processor 1704 when executingsoftware. The processing system 1714 further includes at least one ofthe components 1604, 1606, 1608, 1610, 1612. The components may besoftware components running in the processor 1704, resident/stored inthe computer readable medium/memory 1706, one or more hardwarecomponents coupled to the processor 1704, or some combination thereof.The processing system 1714 may be a component of the UE 350 and mayinclude the memory 360 and/or at least one of the TX processor 368, theRX processor 356, and the controller/processor 359.

In one configuration, the apparatus 1602/1602′ for wirelesscommunication includes means for receiving a second type of data orcontrol information carried in at least two subslots bundled within asubframe, and the second type of data or control information ispunctured into a first type of data or control information. The subframemay include a portion for carrying ACK/NACK information associated withthe second type of data or control information. The apparatus 1602/1602′may further include means for determining ACK/NACK information for thesecond type of data or control information carried in the bundled atleast two subslots. The apparatus 1602/1602′ may further include meansfor sending the ACK/NACK information during the portion of the subframefor carrying ACK/NACK information.

In an aspect, the apparatus 1602/1602′ may include means for receivingthe second type of data or control information during a rescheduledsubslot when the ACK/NACK information indicates a negativeacknowledgement. In an aspect, the ACK/NACK information is carried on aneMBB uplink common burst channel. In an aspect, the first type of datais associated with eMBB and the second type of data is associated withURLLC.

The aforementioned means may be one or more of the aforementionedcomponents of the apparatus 1602 and/or the processing system 1714 ofthe apparatus 1602′ configured to perform the functions recited by theaforementioned means. As described supra, the processing system 1714 mayinclude the TX Processor 368, the RX Processor 356, and thecontroller/processor 359. As such, in one configuration, theaforementioned means may be the TX Processor 368, the RX Processor 356,and the controller/processor 359 configured to perform the functionsrecited by the aforementioned means.

Further disclosure is included in the Appendix.

It is understood that the specific order or hierarchy of blocks in theprocesses/flowcharts disclosed is an illustration of exemplaryapproaches. Based upon design preferences, it is understood that thespecific order or hierarchy of blocks in the processes/flowcharts may berearranged. Further, some blocks may be combined or omitted. Theaccompanying method claims present elements of the various blocks in asample order, and are not meant to be limited to the specific order orhierarchy presented.

The previous description is provided to enable any person skilled in theart to practice the various aspects described herein. Variousmodifications to these aspects will be readily apparent to those skilledin the art, and the generic principles defined herein may be applied toother aspects. Thus, the claims are not intended to be limited to theaspects shown herein, but is to be accorded the full scope consistentwith the language claims, wherein reference to an element in thesingular is not intended to mean “one and only one” unless specificallyso stated, but rather “one or more.” The word “exemplary” is used hereinto mean “serving as an example, instance, or illustration.” Any aspectdescribed herein as “exemplary” is not necessarily to be construed aspreferred or advantageous over other aspects. Unless specifically statedotherwise, the term “some” refers to one or more. Combinations such as“at least one of A, B, or C,” “one or more of A, B, or C,” “at least oneof A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or anycombination thereof” include any combination of A, B, and/or C, and mayinclude multiples of A, multiples of B, or multiples of C. Specifically,combinations such as “at least one of A, B, or C,” “one or more of A, B,or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and“A, B, C, or any combination thereof” may be A only, B only, C only, Aand B, A and C, B and C, or A and B and C, where any such combinationsmay contain one or more member or members of A, B, or C. All structuraland functional equivalents to the elements of the various aspectsdescribed throughout this disclosure that are known or later come to beknown to those of ordinary skill in the art are expressly incorporatedherein by reference and are intended to be encompassed by the claims.Moreover, nothing disclosed herein is intended to be dedicated to thepublic regardless of whether such disclosure is explicitly recited inthe claims. The words “module,” “mechanism,” “element,” “device,” andthe like may not be a substitute for the word “means.” As such, no claimelement is to be construed as a means plus function unless the elementis expressly recited using the phrase “means for.”

What is claimed is:
 1. A method of wireless communication by a basestation, the method comprising: puncturing, in at least one minislot,data or control information associated with a first type of traffic withdata or control information associated with a second type of traffic;bundling the at least one minislot within a subframe, wherein thesubframe includes a portion for carrying acknowledgment (ACK)/negativeacknowledgment (NACK) information associated with the data or controlinformation associated with the second type of traffic; andcommunicating with a user equipment (UE) during the at least oneminislot within the subframe.
 2. The method of claim 1, furthercomprising: receiving ACK/NACK information associated with the data orcontrol information associated with the second type of traffic carriedin the at least one minislots.
 3. The method of claim 2, wherein theACK/NACK information is carried on an enhanced mobile broadband (eMBB)uplink common burst channel.
 4. The method of claim 2, furthercomprising: rescheduling the data or control information associated withthe second type of traffic when the ACK/NACK information indicates aNACK; and sending the rescheduled data or control information associatedwith the second type of traffic.
 5. The method of claim 1, furthercomprising: sending, to a neighboring base station, informationindicating a configuration of the portion for carrying the ACK/NACKinformation associated with the data or control information associatedwith the second type of traffic.
 6. The method of claim 1, wherein thefirst type of traffic is associated with eMBB and the second type oftraffic is associated with ultra-reliable low-latency communication(URLLC).
 7. The method of claim 1, wherein each minislot of one or moreminislots of the at least one minislot includes one of two or foursymbols.
 8. A method of wireless communication by a user equipment (UE),the method comprising: receiving data or control information associatedwith a second type of traffic carried in at least one mini slot bundledwithin a subframe, wherein the data or control information is puncturedinto data or control information associated with a first type oftraffic, and wherein the subframe includes a portion for carryingacknowledgment (ACK)/negative acknowledgment (NACK) informationassociated with the data or control information associated with thesecond type of traffic; determining ACK/NACK information for the data orcontrol information associated with the second type of traffic carriedin the at least one minislot; and sending the ACK/NACK informationduring the portion of the subframe for carrying ACK/NACK information. 9.The method of claim 8, further comprising: receiving the data or controlinformation associated with the second type of traffic during arescheduled mini slot when the ACK/NACK information indicates a NACK.10. The method of claim 8, wherein the ACK/NACK information is carriedon an enhanced mobile broadband (eMBB) uplink common burst channel. 11.The method of claim 8, wherein the first type of traffic is associatedwith eMBB and the second type of traffic is associated withultra-reliable low-latency communication (URLLC).
 12. The method ofclaim 8, wherein each minislot of one or more minislots of the at leastone minislot includes one of two or four symbols.
 13. An apparatus forwireless communication by a base station, the apparatus comprising: amemory; and at least one processor coupled to the memory and configuredto: puncture, in at least one minislot, data or control informationassociated with a first type of traffic with data or control informationassociated with a second type of traffic; bundle the at least oneminislot within a subframe, wherein the subframe includes a portion forcarrying acknowledgment (ACK)/negative acknowledgment (NACK) informationassociated with the data or control information associated with thesecond type of traffic; and communicate with a user equipment (UE)during the at least one minislot within the subframe.
 14. The apparatusof claim 13, wherein the at least one processor is further configuredto: receive ACK/NACK information associated with the data or controlinformation associated with the second type of traffic carried in the atleast one minislots.
 15. The apparatus of claim 14, wherein the ACK/NACKinformation is carried on an enhanced mobile broadband (eMBB) uplinkcommon burst channel.
 16. The apparatus of claim 14, wherein the atleast one processor is further configured to: reschedule the data orcontrol information associated with the second type of traffic when theACK/NACK information indicates a NACK; and send the rescheduled data orcontrol information associated with the second type of traffic.
 17. Theapparatus of claim 13, wherein the at least one processor is furtherconfigured to: send, to a neighboring base station, informationindicating a configuration of the portion for carrying the ACK/NACKinformation associated with the data or control information associatedwith the second type of traffic.
 18. The apparatus of claim 13, whereinthe first type of traffic is associated with eMBB and the second type oftraffic is associated with ultra-reliable low-latency communication(URLLC).
 19. The apparatus of claim 13, wherein each minislot of one ormore minislots of the at least one minislot includes one of two or foursymbols.
 20. An apparatus for wireless communication by a user equipment(UE), the apparatus comprising: a memory; and at least one processorcoupled to the memory and configured to: receive data or controlinformation associated with a second type of traffic carried in at leastone mini slot bundled within a subframe, wherein the data or controlinformation is punctured into data or control information associatedwith a first type of traffic, and wherein the subframe includes aportion for carrying acknowledgment (ACK)/negative acknowledgment (NACK)information associated with the data or control information associatedwith the second type of traffic; determine ACK/NACK information for thedata or control information associated with the second type of trafficcarried in the at least one minislot; and send the ACK/NACK informationduring the portion of the subframe for carrying ACK/NACK information.21. The apparatus of claim 20, wherein the at least one processor isfurther configured to: receive the data or control informationassociated with the second type of traffic during a rescheduled minislotwhen the ACK/NACK information indicates a NACK.
 22. The apparatus ofclaim 20, wherein the ACK/NACK information is carried on an enhancedmobile broadband (eMBB) uplink common burst channel.
 23. The apparatusof claim 20, wherein the first type of traffic is associated with eMBBand the second type of traffic is associated with ultra-reliablelow-latency communication (URLLC).
 24. The apparatus of claim 20,wherein each minislot of one or more minislots of the at least oneminislot includes one of two or four symbols.